ROX-32232: Add task to check if fbc catalogs are within current max sizes #307
+62
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kurlov
commented
Jan 22, 2026
msugakov
changed the title
msugakov
reviewed
Jan 22, 2026
Contributor
msugakov
left a comment
msugakov
left a comment
There was a problem hiding this comment.
I likely will find more in subsequent iterations.
Co-authored-by: Misha Sugakov <537715+msugakov@users.noreply.github.com>
Contributor
|
Caution There are some errors in your PipelineRun template.
|
Closed
msugakov
reviewed
Jan 23, 2026
Co-authored-by: Misha Sugakov <537715+msugakov@users.noreply.github.com>
msugakov
approved these changes
Jan 23, 2026
kurlov
deleted the
akurlov/ROX-32232-notify-when-fbc-file-sizes-reach-limits
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a new task to notify when ACS FBC reach the current max sizes.
ACS operator catalog is the third biggest FBC at the movement. We should know when ACS FBCs grow to the current max sizes. Because it might introduces challenges for OLM and installation/upgrade might not work properly. So basically this task is just a warning/sanity check to take actions if necessary. Either just bump the limit or investigate further is big FBC size introduce any trouble for OLM
Current biggest catalogs for the old format (opm < 1.28.0, ocp < 4.15):
And the biggerst catalogs for the new format (opm 1.28.0+, ocp 4.15+):
Based on those findings I set the max sizes accordingly